Optimizing bandwidth usage and improving performance for web page caching

ABSTRACT

Improving of bandwidth usage and performance for web page caching. Responsive to a subsequent request for a web page, a server only returns the set of web page portions of the requested web page that are not in a browser cache, have expired, and/or have changed.

BACKGROUND

The present invention relates generally to the field of electricalcomputers and digital processing systems, and more particularly tomulticomputer data transfer.

Web pages contain both static data and dynamic data. Static datagenerally remains constant for extended time periods and is usuallyconsistent among different pages within a single domain. Dynamic datamay change based on a variety of contextual factors, varies based oneach web page request, and is different among web pages within in asingle domain.

Web pages are not developed as a monolith. A web page is divided intosmaller fragments which render specific information on the page. Eachweb page portion, the smallest fragment or sub-fragment that is notfurther subdivided, is either static or dynamic. When a web page isgenerated, the main page along with all the web page portions areexecuted. A server storing the web page and the web page portions has acaching policy for each web page portion. Upon a request, the serverstitches the web page portions into a whole and transmits the web page.

SUMMARY

According to an aspect of the present invention, there is a method,computer program product, and/or system that performs the followingsteps (not necessarily in the following order): (i) receiving, from arequestor a request for a subsequent web page, the request including afirst web page set of metadata; (ii) determining a set of current webpage portions based, at least in part, on the first web page set ofmetadata; and (iii) sending the set of current web page portions to therequestor. The subsequent web page includes the set of current web pageportions. At least the determining step is performed by computersoftware running on computer hardware.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram view of a first embodiment of a systemaccording to the present invention;

FIG. 2 is a flowchart showing a first embodiment method performed, atleast in part, by the first embodiment system;

FIG. 3 is a block diagram view of a machine logic (for example,software) portion of the first embodiment system for performing at leastsome of the method steps in FIG. 2;

FIG. 4 is a flowchart showing a second embodiment method performed, atleast in part, by the first embodiment system;

FIG. 5 is a block diagram view of a machine logic (for example,software) portion of the first embodiment system for performing at leastsome of the method steps in FIG. 4;

FIG. 6 is a diagram view depicting a web page according to an embodimentof the present invention that is helpful in understanding embodiments ofthe present invention;

FIG. 7 is a block diagram of a second embodiment of a system accordingto the present invention;

FIG. 8 is a flowchart showing a third embodiment method performed, atleast in part by a third embodiment of a system according to the presentinvention; and

FIG. 9 is a flowchart showing a fourth embodiment method performed, atleast in part by a fourth embodiment of a system according to thepresent invention.

DETAILED DESCRIPTION

Improving of bandwidth usage and performance for web page caching.Responsive to a subsequent request for a web page, a server only returnsthe set of web page portions of the requested web page that are not in abrowser cache, have expired, and/or have changed. This DetailedDescription section is divided into the following sub-sections: (i) TheHardware and Software Environment; (ii) Example Embodiment; (iii) SecondExample Embodiment; (iv) Further Comments and/or Embodiments; and (v)Definitions.

I. The Hardware and Software Environment

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

An embodiment of a possible hardware and software environment forsoftware and/or methods according to the present invention will now bedescribed in detail with reference to the Figures. FIG. 1 is afunctional block diagram illustrating various portions of networkedcomputers system 100, including: web page server sub-system 102; browsersub-systems 104, 106, 108, 110; communication network 114; web pageserver computer 200; communication unit 202; processor set 204;input/output (I/O) interface set 206; memory device 208; persistentstorage device 210; display device 212; external devices 214; randomaccess memory (RAM) devices 230; cache memory device 232; browser cache240; web page server program 300; and browser caching program 500.

Web page server sub-system 102 is, in many respects, representative ofthe various computer sub-system(s) in the present invention.Accordingly, several portions of web page server sub-system 102 will nowbe discussed in the following paragraphs.

Web page server sub-system 102 may be a laptop computer, tabletcomputer, netbook computer, personal computer (PC), a desktop computer,a personal digital assistant (PDA), a smart phone, or any programmableelectronic device capable of communicating with the client sub-systemsvia communication network 114. Web page server program 300 is acollection of machine readable instructions and/or data that is used tocreate, manage and control certain software functions that will bediscussed in detail, below, in the Example Embodiment sub-section ofthis Detailed Description section.

Web page server sub-system 102 is capable of communicating with othercomputer sub-systems via communication network 114. Communicationnetwork 114 can be, for example, a local area network (LAN), a wide areanetwork (WAN) such as the Internet, or a combination of the two, and caninclude wired, wireless, or fiber optic connections. In general,communication network 114 can be any combination of connections andprotocols that will support communications between server and clientsub-systems.

Web page server sub-system 102 is shown as a block diagram with manydouble arrows. These double arrows (no separate reference numerals)represent a communications fabric, which provides communications betweenvarious components of web page server sub-system 102. Thiscommunications fabric can be implemented with any architecture designedfor passing data and/or control information between processors (such asmicroprocessors, communications and network processors, etc.), systemmemory, peripheral devices, and any other hardware components within asystem. For example, the communications fabric can be implemented, atleast in part, with one or more buses.

Memory device 208 and persistent storage device 210 arecomputer-readable storage media. In general, memory device 208 caninclude any suitable volatile or non-volatile computer-readable storagemedia. It is further noted that, now and/or in the near future: (i)external devices 214 may be able to supply, some or all, memory for webpage server sub-system 102; and/or (ii) devices external to web pageserver sub-system 102 may be able to provide memory for web page serversub-system 102.

Web page server program 300 is stored in persistent storage device 210for access and/or execution by one or more processors of processor set204, usually through memory device 208. Persistent storage device 210:(i) is at least more persistent than a signal in transit; (ii) storesthe program (including its soft logic and/or data), on a tangible medium(such as magnetic or optical domains); and (iii) is substantially lesspersistent than permanent storage. Alternatively, data storage may bemore persistent and/or permanent than the type of storage provided bypersistent storage device 210.

Web page server program 300 may include both machine readable andperformable instructions and/or substantive data (that is, the type ofdata stored in a database). In this particular embodiment, persistentstorage device 210 includes a magnetic hard disk drive. To name somepossible variations, persistent storage device 210 may include a solidstate hard drive, a semiconductor storage device, read-only memory(ROM), erasable programmable read-only memory (EPROM), flash memory, orany other computer-readable storage media that is capable of storingprogram instructions or digital information.

The media used by persistent storage device 210 may also be removable.For example, a removable hard drive may be used for persistent storagedevice 210. Other examples include optical and magnetic disks, thumbdrives, and smart cards that are inserted into a drive for transfer ontoanother computer-readable storage medium that is also part of persistentstorage device 210.

Communication unit 202, in these examples, provides for communicationswith other data processing systems or devices external to web pageserver sub-system 102. In these examples, communication unit 202includes one or more network interface cards. Communication unit 202 mayprovide communications through the use of either or both physical andwireless communications links. Any software modules discussed herein maybe downloaded to a persistent storage device (such as persistent storagedevice 210) through a communications unit (such as communication unit202).

I/O interface set 206 allows for input and output of data with otherdevices that may be connected locally in data communication with webpage server computer 200. For example, I/O interface set 206 provides aconnection to external devices 214. External devices 214 will typicallyinclude devices such as a keyboard, keypad, a touch screen, and/or someother suitable input device. External devices 214 can also includeportable computer-readable storage media such as, for example, thumbdrives, portable optical or magnetic disks, and memory cards. Softwareand data used to practice embodiments of the present invention, forexample, web page server program 300, can be stored on such portablecomputer-readable storage media. In these embodiments the relevantsoftware may (or may not) be loaded, in whole or in part, ontopersistent storage device 210 via I/O interface set 206. I/O interfaceset 206 also connects in data communication with display device 212.

Display device 212 provides a mechanism to display data to a user andmay be, for example, a computer monitor or a smart phone display screen.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

II. Example Embodiment

FIG. 2 shows flowchart 250 depicting a method according to someembodiments of the present invention. FIG. 3 shows web page serverprogram 300, which performs at least some of the method steps offlowchart 250. This method and associated software will now bediscussed, over the course of the following paragraphs, with extensivereference to FIG. 2 (for the method step blocks) and FIG. 3 (for thesoftware blocks). In this example web page server sub-system 102receives requests for a first web page and a subsequent web page.Reference to FIG. 6 is helpful in understanding discussion of web pageportions (fragments and sub-fragments) and caching.

Processing begins at step S255, where receive first request module(“mod”) 302 receives a request for a first web page. In some embodimentsof the present invention, the first web page is one web page of a set ofweb pages on a domain. In some embodiments of the present invention, thefirst web page is the only web page on a domain.

Processing proceeds to step S260, where first web page return mod 304returns or provides the requestor the first web page. In this example,first web page return mod 304 also returns a first web page set ofmetadata with the first web page. In this example, the first web pageset of metadata includes: (i) a set of fragment and/or sub-fragment (aset of web page portion) definitions; (ii) a set of request dates; (iii)a set of expiration dates; and (iv) a set of caching policies. In someembodiments of the present invention, the first web page consists of aset of web page portions. Alternatively, the first webpage set ofmetadata includes, but is not limited to: (i) a set of web page portiondefinitions; (ii) a set of request dates; (iii) a set of expirationdates; (iv) a set of caching policies; (v) a set of related web pages;(vi) a set of related advertisements; (vii) a site map; and/or (viii) amain content fragment.

In some embodiments of the present invention, the set of web pageportion definitions includes definitions of a set of web page portionsof the first web page. In some embodiments of the present invention, acaching policy for a web page portion is one of: (i) never cache (e.g.,for dynamic advertising); (ii) cache inline with a main content fragment(e.g., a web page hierarchy); and (iii) cache individually (e.g., a webpage footer). In some embodiments of the present invention, the set ofrequest dates are individualized for each web page portion of the set ofweb page portions. In some embodiments of the present invention, the setof expiration dates are individualized for each web page portion of theset of web page portions. In some embodiments of the present invention,the set of related web pages includes all other web pages on the samedomain as the first web page. In some embodiments of the presentinvention the set of related advertisements relate to the main contentfragment of the first web page.

Processing proceeds to step S265, where receive subsequent request mod306 receives a request for a subsequent web page. In this example, therequest for the subsequent web page includes a set of metadata. In someembodiments of the present invention, receive subsequent request mod 306does not receive any metadata. In this example, the subsequent web pageis a later-in-time version of the first web page. In some embodiments ofthe present invention, the subsequent web page is a different web pageon the same domain as the first web page. In some embodiments of thepresent invention, the set of metadata received is the first webpage setof metadata. In some embodiments of the present invention, the set ofmetadata received is a subset of the first webpage set of metadata. Insome embodiments of the present invention, the subsequent request is asecond request. Alternatively, the subsequent request is a third orlater request.

Processing proceeds to step S270, where analyze metadata mod 308analyzes the set of metadata received. In this example, the set ofmetadata received by receive subsequent request mod 306 corresponds tothe subsequent web page. In some embodiments of the present invention,the set of metadata received by receive subsequent request mod 306corresponds to a web page on the same domain as the subsequent web page.In some embodiments of the present invention, the subsequent web page isone of the set of related web pages in the metadata. In some embodimentsof the present invention, analyze metadata mod 308 determines that asubset of the set of web page portions must be returned to the requestorbecause, after the set of request dates corresponding to that subset ofthe set of web page portions, the content presented in those web pageportions changed. In some embodiments of the present invention, analyzemetadata mod 308 determines that a subset of the set of web pageportions must be returned to the requestor because, the set ofexpiration dates corresponding to that subset of the set of web pageportions has passed.

In some embodiments of the present invention, analyze metadata mod 308determines that the set of expiration dates corresponding to thesubsequent web page have all passed, and, therefore, analyze metadatamod 308 treats the subsequent request as a first request and processingreturns to step S255. In some embodiments of the present invention,analyze metadata mod 308 determines that the set of web page portiondefinitions in the set of metadata does not match the set of web pageportion definitions corresponding to the subsequent web page, and,therefore, analyze metadata mod 308 treats treat the subsequent requestas a first request, and processing returns to step S255. In someembodiments of the present invention, analyze metadata mod 308determines that there is no set of metadata received, and processingreturns to step S255.

In some embodiments of the present invention, analyze metadata mod 308determines that a subset of the set of web page portions must bereturned to the requestor because that subset of the set of web pageportions was not properly cached pursuant to the set of cachingpolicies. In some embodiments of the present invention, analyze metadatamod 308 determines that a subset of the set of web page portions must bereturned to the requestor because that subset of the set of web pageportions are never cached. In some embodiments of the present invention,analyze metadata mod 308 determines that a subset of the set of web pageportions (the set of web page portions cached inline) must be returnedto the requestor because, after the request date of the set of requestdates corresponding to the main content fragment, the content presentedin the main content fragment changed.

Processing terminates at step S275, where subsequent web page return mod310 returns or provides the requestor a subset of the subsequent webpage. In this example, subsequent web page return mod 310 also returns asubsequent web page set of metadata with the subset of the subsequentweb page. In this example, the subsequent web page set of metadataincludes: (i) a set of web page portion definitions; (ii) a set ofrequest dates; (iii) a set of expiration dates; and (iv) a set ofcaching policies. In some embodiments of the present invention, thesubsequent web page consists of a set of web page portions. In someembodiments of the present invention, subsequent web page return mod 310returns only certain web page portions of the subsequent web page basedon the analysis of the set of metadata by analyze metadata mod 308 instep S270. In some embodiments of the present invention, the subsequentwebpage set of metadata includes, but is not limited to: (i) a set ofweb page portion definitions; (ii) a set of request dates; (iii) a setof expiration dates; (iv) a set of caching policies; (v) a set ofrelated web pages; (vi) a set of related advertisements; (vii) a sitemap; and/or (viii) a main content fragment.

In some embodiments of the present invention, the set of web pageportion definitions includes definitions of a set of web page portionsof the subsequent web page. In some embodiments of the presentinvention, a caching policy for a web page portion of the set of webpage portions is one of: (i) never cache (e.g., for dynamicadvertising); (ii) cache inline with a main content fragment (e.g., aweb page hierarchy); and (iii) cache individually (e.g., a web pagefooter). In some embodiments of the present invention, the set ofrequest dates are individualized for each web page portion of the set ofweb page portions. In some embodiments of the present invention, the setof expiration dates are individualized for each web page portion of theset of web page portions. In some embodiments of the present invention,the set of related web pages includes all other web pages on the samedomain as the subsequent web page. In some embodiments of the presentinvention the set of related advertisements relate to the main contentfragment of the subsequent web page.

III. Second Example Embodiment

FIG. 4 shows flowchart 400 depicting a method according to someembodiments of the present invention. FIG. 5 shows browser cachingprogram 500, which performs at least some of the method steps offlowchart 400. This method and associated software will now bediscussed, over the course of the following paragraphs, with extensivereference to FIG. 4 (for the method step blocks) and FIG. 5 (for thesoftware blocks). In this example browser sub-system 104 requests afirst web page and a subsequent web page from web page server sub-system102. Reference to FIG. 6 is helpful in understanding discussion of webpage portions (fragments and sub-fragments) and caching.

Processing begins at step S405, where first request mod 502 submits arequest for a first web page. In some embodiments of the presentinvention, the first web page is one web page of a set of web pages on adomain. In some embodiments of the present invention, the first web pageis the only web page on a domain.

Processing proceeds to step S410, where receive first web page mod 504receives the first web page. In this example, receive first web page mod504 also receives a first web page set of metadata with the first webpage. In this example, the first web page set of metadata includes: (i)a set of web page portion definitions; (ii) a set of request dates;(iii) a set of expiration dates; and (iv) a set of caching policies. Insome embodiments of the present invention, the first web page consistsof a set of web page portions. In some embodiments of the presentinvention, the first webpage set of metadata includes, but is notlimited to: (i) a set of web page portion definitions; (ii) a set ofrequest dates; (iii) a set of expiration dates; (iv) a set of cachingpolicies; (v) a set of related web pages; (vi) a set of relatedadvertisements; (vii) a site map; and/or (viii) a main content fragment.

In some embodiments of the present invention, the set of web pageportion definitions includes definitions of a set of web page portionsof the first web page. In some embodiments of the present invention, acaching policy for a web page portion of the set of web page portions isone of: (i) never cache (e.g., for dynamic advertising); (ii) cacheinline with a main content fragment (e.g., a web page hierarchy); and(iii) cache individually (e.g., a web page footer). In some embodimentsof the present invention, the set of request dates are individualizedfor each web page portion of the set of web page portions. In someembodiments of the present invention, the set of expiration dates areindividualized for each web page portion of the set of web pageportions. In some embodiments of the present invention, the set ofrelated web pages includes all other web pages on the same domain as thefirst web page. In some embodiments of the present invention the set ofrelated advertisements relate to the main content fragment of the firstweb page.

Processing proceeds to step S415, where first cache mod 506 caches thefirst web page. In this example, first cache mod 506 caches the firstweb page according to the set of caching policies in the first web pageset of metadata. In some embodiments of the present invention, firstcache mod 506 stores the first web page to browser cache 240 (FIG. 1).Alternatively, the first web page is cached in other locations withinbrowser sub-system 104. In some embodiments of the present invention,first cache mod 506 caches the first web page as a single unit.Alternatively, first cache mod 506 caches each web page portion of theset of web page portions of the first web page as an independent unit.In some embodiments of the present invention, the first web page iscached such that browser sub-system 104 independently accesses each webpage portion of the set of web page portions of the first web page.

Processing proceeds to step S420, where subsequent request mod 508submits a request for a subsequent web page. In this example, thesubsequent web page is the same web page as the first web page. In someembodiments of the present invention, the subsequent web page is adifferent web page on the same domain as the first web page. In someembodiments of the present invention, the subsequent request is a secondrequest. Alternatively, the subsequent request is a third or laterrequest. In some embodiments of the present invention, the subsequentweb page is one web page of a set of web pages on a domain. In someembodiments of the present invention, the subsequent web page is theonly web page on a domain. In this example, the request for thesubsequent web page includes a set of metadata. In some embodiments ofthe present invention, the set of metadata is the first web page set ofmetadata. In some embodiments of the present invention, the set ofmetadata is a subset of the first web page set of metadata. In someembodiments of the present invention, the “first web page set ofmetadata” corresponds to a set of prior web pages.

Processing proceeds to step S425, where subsequent web page mod 510receives a subset of the subsequent web page. In this example,subsequent web page mod 510 also receives a subsequent web page set ofmetadata with the subset of the subsequent web page. In this example,the subsequent web page set of metadata includes: (i) a set of web pageportion definitions; (ii) a set of request dates; (iii) a set ofexpiration dates; and (iv) a set of caching policies. In someembodiments of the present invention, the subsequent web page consistsof a set of web page portions. In some embodiments of the presentinvention, subsequent web page mod 510 receives only the subset of thesubsequent web page, based on the metadata submitted in step S420. Insome embodiments of the present invention, the subsequent webpage set ofmetadata includes, but is not limited to: (i) a set of web page portiondefinitions; (ii) a set of request dates; (iii) a set of expirationdates; (iv) a set of caching policies; (v) a set of related web pages;(vi) a set of related advertisements; (vii) a site map; and/or (viii) amain content fragment.

In some embodiments of the present invention, the set of web pageportion definitions includes definitions of a set of web page portionsof the subsequent web page. In some embodiments of the presentinvention, a caching policy for a web page portion of the set of webpage portions is one of: (i) never cache (e.g., for dynamicadvertising); (ii) cache inline with a main content fragment (e.g., aweb page hierarchy); and (iii) cache individually (e.g., a web pagefooter). In some embodiments of the present invention, the set ofrequest dates are individualized for each web page portion of the set ofweb page portions. In some embodiments of the present invention, the setof expiration dates are individualized for each web page portion of theset of web page portions. In some embodiments of the present invention,the set of related web pages includes all other web pages on the samedomain as the subsequent web page. In some embodiments of the presentinvention the set of related advertisements relate to the main contentfragment of the subsequent web page.

Processing proceeds to step S430, where stitch mod 512 stitchestogether, or combines, the subsequent web page. In this example, stitchmod 512 combines the subset of the subsequent web page received bysubsequent web page mod 510 in step S425 with the subset of the firstweb page stored in the cache by first cache mod 506 in step S415. Insome embodiments of the present invention, stitch mod 512 retrieves asubset of the set of web page portions from the first web page frommemory. In some embodiments of the present invention, stitch mod 512determines that a subset of the set of web page portions from the firstweb page are not used to stitch together the subsequent web page. Insome embodiments of the present invention, the “first web page” includesa set of prior web pages.

Processing terminates at step S435, where subsequent cache mod 514caches the subsequent web page. In this example, subsequent cache mod514 caches the subsequent web page according to the set of cachingpolicies in the subsequent web page set of metadata. In some embodimentsof the present invention, subsequent cache mod 514 stores the subsequentweb page to browser cache 240 (FIG. 1). Alternatively, the subsequentweb page is cached in other locations within browser sub-system 104. Insome embodiments of the present invention, subsequent cache mod 514caches the subsequent web page as a single unit. Alternatively,subsequent cache mod 514 caches each web page portion of the set of webpage portions of the subsequent web page as an independent unit. In someembodiments of the present invention, the subsequent web page is cachedsuch that browser sub-system 104 independently accesses each web pageportion of the set of web page portions of the subsequent web page. Insome embodiments of the present invention, a subset of the set of webpage portions of the subsequent web page are already stored to cache. Insome embodiments of the present invention, subsequent cache mod 514deletes a subset of the first web page from the cache, the subset of thefirst web page corresponding to the set of current web page portions.

IV. Further Comments and/or Embodiments

Some embodiments of the present invention recognize the following facts,potential problems, and/or potential areas for improvement with respectto the current state of the art: (i) a browser is unable to analyze acache to identify a set of web page portions that is missing, changed,and/or expired; (ii) a browser is unable to request only a set of webpage portions that is missing and/or expired; (iii) a server responds toa request from a browser for a web page by returning the entire web pageto the browser; and/or (iv) a server requires a higher bandwidth totransmit a web page that is requested more frequently, even if thecontent of the web page does not change. Some embodiments of the presentinvention recognize that caching improves the response time and reducesthe load on a server, though it does not optimize the network bandwidthusage. Some embodiments of the present invention recognize that the dataexchanged between the server and the user remains the same despitecaching.

FIG. 6 is a diagram view depicting web page 600 according to anembodiment of the present invention. Web page 600 includes: header 605;category hierarchy 610; main content 615; marketing 620; and footer 635.Each of these parts of web page 600 is a fragment. Marketing 620includes: static marketing 625; and dynamic marketing 630. Each of theseparts of marketing 620 is a sub-fragment.

In this example, web page 600 has a total size of 200 kB. Web page 600is one of many web pages that make up a domain (e.g., www.domain.com)and each web page on the domain has a constituent set of web pageportions (i.e., fragments and/or sub-fragments). Web page 600 includesmain content 615. Main content 615 is independently cached, has a sizeof 60 kB, and has a thirty percent probability of changing between afirst request and a subsequent request. Main content 615 will bestitched as part of the subsequent web page if a subsequent request ismade for web page 600. If the subsequent request is made for a differentweb page on the domain, main content 615 will not be stitched as part ofthe subsequent web page.

Web page 600 also includes header 605 and static marketing 625 (asub-fragment of marketing 620), which are cached inline with maincontent 615. Header 605 has a size of 70 kB and a ten percentprobability of changing between a first request and a subsequentrequest. Static marketing 625 has a size of 15 kB and a five percentprobability of changing between a first request and a subsequentrequest. Each web page on the domain has a different main content. Theheader and static marketing for each web page are dependent on the maincontent for that page. Header 605 and static marketing 625 will bereused for and stitched as part of the subsequent web page if asubsequent request is made for web page 600. If the subsequent requestis made for a different web page on the domain, header 605 and staticmarketing 625 will not be stitched as part of the subsequent web page.

Web page 600 also includes category hierarchy 610 and footer 635, whichare cached independently of main content 615. Category hierarchy 610 hasa size of 20 kB and has a thirty percent probability of changing betweena first request and a subsequent request. Footer 635 has a size of 20 kBand has a zero percent chance of changing between a first request and asubsequent request. In some embodiments of the present invention,category hierarchy 610 and footer 635 are cached inline with oneanother. Each web page on the domain reuses the same category hierarchyand footer. Therefore, these fragments will be will be reused for andstitched as part of the subsequent web page if the subsequent request ismade for a different web page on the same domain.

Marketing 620 also includes dynamic marketing 630, which is nevercached. Dynamic marketing 630 has a size of 15 kB and has a one-hundredpercent chance of changing between a first request and a subsequentrequest. Dynamic marketing 630 may not bear any relation to main content615. In some embodiments of the present invention, dynamic marketing 630is provided to the domain by an advertiser or a sponsor. Dynamicmarketing 630 will never be stitched as part of a subsequent web page.

Based on the size of web page 600 (and the constituent web pageportions) and the probability of each web page portion changing betweena first request and a subsequent request, the approximate bandwidthsavings for a subsequent request of a web page are able to be estimated.In this example, the bandwidth savings occur when a web page portiondoes not change between a first request and a subsequent request. Onaverage, main content 615 does not change between seventy percent ofrequests, resulting in a savings of 42 kB per request (0.7×60 kB perrequest). For the remaining web page portions of web page 600, theaverage savings are: (i) header 605, 63 kB (0.9×70 kB per request); (ii)static marketing 625, 14.25 kB (0.95×15 kb); (iii) category hierarchy610, 14 kB (0.7×20 kB); (iv) footer 635, 20 kB (1.0×20 kB); and (v)dynamic marketing 630, 0 kB (0.0×15 kB). In total, the average savingsfor each request of web page 600 is 153.25 kB of 200 kB (or 76.625%).

FIG. 7 shows web page request environment 700 depicting a secondembodiment of a system according to the present invention. In thisexample, browser sub-system 104 submits a request for a web page fromweb page server sub-system 102 and web page server sub-system 102returns a subset of the web page to browser sub-system 104. Browsersub-system 104 includes browser cache 240. Web page server sub-system102 includes: set of web pages 702; caching policies 706; and portiondefinitions 704.

Browser sub-system 104 submits a request for a web page to web pageserver sub-system 706 over data communication 715. Web page serversub-system 102 determines what web page portions must be returned tobrowser sub-system 104, based in part on information stored in cachingpolicies 706 and portion definitions 704. Web page server sub-system 102returns a subset of the web page to browser sub-system 104 over datacommunication 720 a and data communication 720 b. In this example, webpage server sub-system 102 returns web page subset 708. Web page subset708 includes: category hierarchy 610; dynamic marketing 630; and set ofmetadata (not separately shown). Based on the set of metadata, browsersub-system 104 determines what pieces of web page subset 708 to store tobrowser cache 240.

FIG. 8 shows flowchart 800, depicting a method for creating a set ofmetadata associated with a web page portion according to someembodiments of the present invention. In this example, the web pageserver sub-system receives a second request for a web page. Flowchart800 is executed for each web page portion (fragment or sub-fragment) onthe web page. In this example, the web page server sub-system analyzesthe request for a static marketing fragment.

Processing beings at step S802, where the web page server sub-systemreceives a request for a set of metadata associated with a web pageportion. In this example, a browser transmitted a request to the webpage server sub-system to invoke a web page. The web page serversub-system has determined that the web page includes a set ofconstituent web page portions and is processing the request for a singleweb page portion. In this example, the web page server sub-system isprocessing the request for the static marketing fragment of the webpage.

Processing proceeds to determination step S804, where the web pageserver sub-system determines whether a web page portion is in a cachefor the browser. In some embodiments of the present invention, the webpage server sub-system analyzes the request from the browser todetermine if the web page portion is in the cache. If the web pageportion is not in the cache, processing proceeds through the “No”branch. If the web page portion is in the cache, processing proceedsthrough the “Yes” branch. In this example, the request included a set ofmetadata relating to contents of the cache. In this example, the staticmarketing fragment of the web page is stored in the cache and processingproceeds through the “Yes” branch.

Following the “No” branch from step S804, processing terminates at stepS806, where the web page server sub-system creates a set of metadata. Insome embodiments of the present invention, creating the set of metadataincludes: (i) a web page portion definition; (ii) a caching policy;and/or (iii) a coded status tag. In some embodiments of the presentinvention, the coded status tag signifies a type of response the webpage server sub-system is sending to the browser. In some embodiments ofthe present invention, the set of metadata is appended to a responsefrom the web page server sub-system to the browser. In some embodimentsof the present invention, processing returns to step S802 for a set ofconstituent sub-fragments making up the web page portion. In thisexample, processing does not proceed to step S806. However, when the webpage server sub-system analyzes the dynamic marketing fragment for theweb page, processing will proceed to step S806.

Following the “Yes” branch from step S804, processing proceeds todetermination step S808, where the web page server sub-system determineswhether the web page portion is cached inline. In some embodiments ofthe present invention, the web page server sub-system analyzes therequest from the browser to determine if the web page portion is cachedinline. If the web page portion is not cached inline, processingproceeds through the “No” branch. If the web page portion is cachedinline, processing proceeds through the “Yes” branch. In this example,the request included a caching policy for the static marketing. In thisexample, the static marketing fragment is cached inline and processingproceeds through the “Yes” branch.

Following the “No” branch from step S808, processing terminates at stepS810, where the web page server sub-system creates a set of metadata. Insome embodiments of the present invention, creating the set of metadataincludes: (i) a web page portion definition; (ii) a caching policy;and/or (iii) a coded status tag. In some embodiments of the presentinvention, the coded status tag signifies a type of response the webpage server sub-system is sending to the browser. In some embodiments ofthe present invention, the set of metadata is appended to a responsefrom the web page server sub-system to the browser. In some embodimentsof the present invention, the web page portion contains a set ofsub-fragments. In some embodiments of the present invention, processingreturns to step S802 for a set of constituent sub-fragments making upthe web page portion. In this example, processing does not proceed tostep S810. However, when the web page server sub-system analyzes thefooter fragment for the web page, processing will proceed to step S810.

Following the “Yes” branch from step S808, processing terminates at stepS812, where the web page server sub-system creates a set of metadata. Insome embodiments of the present invention, creating the set of metadataincludes: (i) a web page portion definition; (ii) a caching policy;and/or (iii) a coded status tag. In some embodiments of the presentinvention, the coded status tag signifies a type of response the webpage server sub-system is sending to the browser. In some embodiments ofthe present invention, the set of metadata is appended to a responsefrom the web page server sub-system to the browser. In some embodimentsof the present invention, the web page server sub-system creates areference to the metadata for the main content fragment of the web page.In some embodiments of the present invention, processing returns to stepS802 for a set of constituent sub-fragments making up the web pageportion. In this example, processing of the static marketing fragmentproceeds to step S812 and the set of metadata includes: (i) a locationon the web page for the static marketing fragment; (ii) an inlinecaching policy; and (iii) a status tag stating indicating that thestatic marketing fragment was not replaced.

FIG. 9 shows flowchart 900, depicting a method for responding to arequest for a web page according to some embodiments of the presentinvention. In this example, the web page server sub-system receives asecond request for a web page. Flowchart 900 is executed for each webpage portion (fragment or sub-fragment) on the web page. In thisexample, the web page server sub-system analyzes the request for a maincontent fragment.

Processing begins at step S902, where the web page server sub-systemreceives a request for a web page portion. In this example, a browsertransmitted a request to the web page server sub-system to invoke a webpage. The web page server sub-system has determined that the web pageincludes a set of constituent web page portions and is processing therequest for a single web page portion. In this example, the web pageserver sub-system is processing the request for the main contentfragment of the web page.

Processing proceeds to determination step S904, where the web pageserver sub-system determines whether the web page portion is in a cachememory of the browser. In some embodiments of the present invention, theweb page server sub-system analyzes a set of metadata from the browserto determine whether the web page portion is in the cache memory. If theweb page portion is not in the cache memory, processing proceeds throughthe “No” branch. If the web page portion is in the cache memory,processing proceeds through the “Yes” branch. In this example, the webpage server sub-system determines that main content fragment is in thecache memory and processing proceeds through the “Yes” branch. However,if the web page portion was overwritten in the cache memory or if theweb page portion was improperly saved in the cache memory, processingproceeds through the “No” branch.

Following the “No” branch from step S904, processing proceeds todetermination step S906, where the web page server sub-system determineswhether the web page portion is ever cached. In some embodiments of thepresent invention, the web page server sub-system analyzes a set ofcaching policies to determine whether the web page portion is evercached. If the web page portion is never cached, processing proceedsthrough the “No” branch. If the web page portion is ever cached,processing proceeds through the “Yes” branch. In this example,processing does not reach step S904. However, if the web page serversub-system is analyzing a dynamic marketing fragment, that fragment isnever cached and processing proceeds through the “No” branch.Alternatively, if the web page server sub-system analyzes the cachingpolicy and determines the web page portion is supposed to be cached,processing proceeds through the “Yes” branch.

Following the “No” branch from step S906, processing terminates at stepS908, where the web page server sub-system executes the web pageportion. In some embodiments of the present invention, the web pageserver sub-system appends the web page portion to a set of content to bereturned to the browser. In some embodiments of the present invention,processing returns to step S902 for a set of constituent sub-fragmentsmaking up the web page portion. In this example, processing does notreach step S908. However, if the web page server is analyzing a dynamicmarketing fragment, the web page server sub-system attaches the dynamicmarketing fragment to a set of content to be returned to the browser.

Following the “Yes” branch from step S904, processing proceeds todetermination step S910, where the web page server sub-system determineswhether the web page portion has expired and/or changed. In someembodiments of the present invention, the web page server sub-systemanalyzes a set of metadata from the browser to determine whether the webpage portion has changed in the time period since the browser lastrequested the web page portion. In some embodiments of the presentinvention, the web page server sub-system analyzes a set of metadatafrom the browser to determine whether the web page portion has expiredin the time period since the browser last requested the web pageportion. If the web page portion has not expired and has not changed,processing proceeds through the “No” branch. If the web page portion hasexpired and/or changed, processing proceeds through the “Yes” branch. Inthis example, the main content fragment has changed since the browserlast requested the web page and processing proceeds through the “Yes”branch. However, if the web page server sub-system is analyzing thefooter fragment, the footer fragment has not expired and has notchanged, therefore processing would proceed through the “No” branch.

Following the “No” branch from step S910, processing terminates at stepS912, where the web page server sub-system updates the set of metadatareturned to the browser. In some embodiments of the present invention,the web page server sub-system appends the updated metadata to a set ofcontent to be returned to the browser. In some embodiments of thepresent invention, the set of metadata pertaining to the web pageportion is updated to reflect: the new request data and/or an update inthe expiration date. In some embodiments of the present invention, theweb page server sub-system does not return the web page portion to thebrowser. In some embodiments of the present invention, processingreturns to step S902 for a set of constituent sub-fragments making upthe web page portion. In this example, processing does not proceed tostep S912. However, if the web page server sub-system is analyzing thefooter fragment, the metadata for the footer fragment is updated toreflect the new request date and the web page server sub-system does notreturn the footer fragment to the browser.

Following the “Yes” branch from step S906, processing terminates at stepS914, where the web page server sub-system executes the web page portionand updates the set of metadata returned to the browser. In someembodiments of the present invention, the web page server sub-systemappends the web page portion to a set of content to be returned to thebrowser. In some embodiments of the present invention, the web pageserver sub-system appends the updated metadata to a set of content to bereturned to the browser. In some embodiments of the present invention,the set of metadata pertaining to the web page portion is updated toreflect: the new request data and/or an update in the expiration date.In some embodiments of the present invention, processing returns to stepS902 for a set of constituent sub-fragments making up the web pageportion. In this example, the main content fragment has changed sincethe browser last requested the web page. The main content fragment isappended to the set of content being returned to the browser.Additionally, the metadata associated with the main content fragment isupdated to reflect: the new definitions of the constituent web pageportions that are included in the main content fragment; the requestdate; and the expiration date. The metadata associated with the maincontent fragment is appended to the set of content being returned to thebrowser.

Some embodiments of the present invention utilize a browser thatimplements a server side caching policy for a web page and cachingheaders to reduce bandwidth usage by the server. In some embodiments ofthe present invention, a server enables a browser to replicate a serverside caching policy used by the server. In some embodiments of thepresent invention, the server reduces the amount of data transmitted toa browser. In some embodiments of the present invention, a browser isaware that a web page is constructed from a set of fragments. In someembodiments of the present invention, a browser is aware of a manner inwhich a set of fragments from a web page is cached by a server. In someembodiments of the present invention, a server only transmits data to abrowser pertaining to a set of sub-fragments from a web page that haveundergone a change.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i) abrowser sends a server a set of metadata for a web page with arequesting for the web page; (ii) a server responds to a browser with anindication of whether a set of fragments from a web page can be reused;(iii) a server responds to a browser with a new set of fragments toreplace a set of fragments that cannot be reused; (iv) a browserassembles a web page by stitching together a set of fragments from acache and a set of fragments received from a server; (v) a browserrequires only a single web page request to assemble the web page; (vi) abrowser implements a server side caching policy to prevent unnecessarydata from being exchanged between a server and the browser; and/or (vii)a browser is aware of a set of fragments present on a web page and a setof caching policies for the set of fragments.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i) abrowser reuses cached fragments of a web page among multiple web pageswithin the same domain; (ii) a server optimizes and reduces bandwidthusage both when a web page is refreshed and when a second web page isrequested within a domain; (iii) a browser detects different web pagefragments, based on metadata from a server; (iv) a browser locallystores web page fragments with correlated metadata; (v) a browserrenders a web page utilizing still-valid locally saved fragments; (vi) aserver indicates which portions of a web page have changed; and/or (vii)a server only transmits fragments of a web page that are required by abrowser.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i) abrowser is aware of a server side caching policy; (ii) a serverindicates to a browser with a set of metadata that a web page contains aset of fragments; (iii) a browser caches a set fragments from a web pagewith an set of metadata associates with the set of fragments; (iv) abrowser sends a request for a web page to a server, the request includesa set of metadata for a set of fragments that make up the web page; (v)a server indicates to a browser whether a set of fragments from a webpage are still valid; (vi) a server transmits a set of fragments from aweb page to a browser for the set of fragments that have changed; and/or(vii) a server transmits a set of metadata for a web page, the set ofmetadata contains definitions for a set of fragments from the web pageand a caching policy for the set of fragments.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i)optimizes network bandwidth usage and reduces response time for loadinga web page; (ii) utilizes a server side caching policy for a web pageand caches headers to reduce bandwidth usage; (iii) saves bandwidthbased on the probability of a set of fragments from a web pageundergoing a change, a size of the set of fragments, and a rate ofviewing of the web page; (iv) generates web pages dynamically byanalyzing parameters for a request for a web page and contextualinformation; (v) caches a web page to prevent dynamic generation of theweb page for each request; (vi) optimizes network bandwidth usage andreduces response time to load a web page; and/or (vii) implements aserver side cache policy on a browser.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i) a serverresponds to a refresh request from a browser with a set of metadatacorrelating to a set of fragments from the web page; (ii) a browsercaches a set of fragments and/or sub-fragments from a web page based ona set of metadata giving an individual caching policy for each fragmentand/or sub-fragment; (iii) a browser caches a web page based on a set ofmetadata received from a server; (iv) a browser updates a set of cacheinformation for a web page based on a set of metadata received from aserver; (v) a browser transmits a set of metadata to a server relatingto a web page, including a date the web page was last refreshed; and/or(vi) a server transmits a set of metadata to a browser relating to a webpage, including a date the web page will expire.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, and/or advantages: (i) a serverrecursively determines whether to transmit a set of fragments from a webpage to a browser based on a set of metadata received from the browser;(ii) a server recursively determines whether to transmit a set offragments from a web page to a browser based on a set of cachingpolicies (e.g., cached inline, cached separately, never cached); and/or(iii) a server transmits a set of metadata to a browser includinginformation that a set of fragments in a cache should be reused.

V. Definitions

Present invention: should not be taken as an absolute indication thatthe subject matter described by the term “present invention” is coveredby either the claims as they are filed, or by the claims that mayeventually issue after patent prosecution; while the term “presentinvention” is used to help the reader to get a general feel for whichdisclosures herein that are believed as maybe being new, thisunderstanding, as indicated by use of the term “present invention,” istentative and provisional and subject to change over the course ofpatent prosecution as relevant information is developed and as theclaims are potentially amended.

Embodiment: see definition of “present invention” above—similar cautionsapply to the term “embodiment.”

And/or: inclusive or; for example, A, B “and/or” C means that at leastone of A or B or C is true and applicable.

Including/include/includes: unless otherwise explicitly noted, means“including, but not necessarily limited to.”

User/subscriber: includes, but is not necessarily limited to, thefollowing: (i) a single individual human; (ii) an artificialintelligence entity with sufficient intelligence to act as a user orsubscriber; and/or (iii) a group of related users or subscribers.

Electrically Connected: means either directly electrically connected, orindirectly electrically connected, such that intervening elements arepresent; an electrical connection may include, but need not be limitedto, elements such as capacitors, inductors, transformers, vacuum tubes,and the like.

Mechanically connected: Includes both direct mechanical connections, andindirect mechanical connections made through intermediate components;includes rigid mechanical connections as well as mechanical connectionthat allows for relative motion between the mechanically connectedcomponents; includes, but is not limited, to welded connections, solderconnections, connections by fasteners (for example, nails, bolts,screws, nuts, hook-and-loop fasteners, knots, rivets, quick-releaseconnections, latches, and/or magnetic connections), force fitconnections, friction fit connections, connections secured by engagementcaused by gravitational forces, pivoting or rotatable connections,and/or slidable mechanical connections.

Data communication: any sort of data communication scheme now known orto be developed in the future, including wireless communication, wiredcommunication, and communication routes that have wireless and wiredportions; data communication is not necessarily limited to: (i) directdata communication; (ii) indirect data communication; and/or (iii) datacommunication where the format, packetization status, medium, encryptionstatus, and/or protocol remains constant over the entire course of thedata communication.

Receive/provide/send/input/output/report: unless otherwise explicitlyspecified, these words should not be taken to imply: (i) any particulardegree of directness with respect to the relationship between theirobjects and subjects; and/or (ii) absence of intermediate components,actions, and/or things interposed between their objects and subjects.

Without substantial human intervention: a process that occursautomatically (often by operation of machine logic, such as software)with little or no human input; some examples that involve “nosubstantial human intervention” include: (i) computer is performingcomplex processing and a human switches the computer to an alternativepower supply due to an outage of grid power so that processing continuesuninterrupted; (ii) computer is about to perform resource intensiveprocessing, and human confirms that the resource-intensive processingshould indeed be undertaken (in this case, the process of confirmation,considered in isolation, is with substantial human intervention, but theresource intensive processing does not include any substantial humanintervention, notwithstanding the simple yes—no style confirmationrequired to be made by a human); and (iii) using machine logic, acomputer has made a weighty decision (for example, a decision to groundall airplanes in anticipation of bad weather), but, before implementingthe weighty decision the computer must obtain simple yes—no styleconfirmation from a human source.

Automatically: without any human intervention.

Module/Sub-Module: any set of hardware, firmware and/or software thatoperatively works to do some kind of function, without regard to whetherthe module is: (i) in a single local proximity; (ii) distributed over awide area; (iii) in a single proximity within a larger piece of softwarecode; (iv) located within a single piece of software code; (v) locatedin a single storage device, memory, or medium; (vi) mechanicallyconnected; (vii) electrically connected; and/or (viii) connected in datacommunication.

Computer: any device with significant data processing and/or machinereadable instruction reading capabilities including, but not limited to:desktop computers, mainframe computers, laptop computers,field-programmable gate array (FPGA) based devices, smart phones,personal digital assistants (PDAs), body-mounted or inserted computers,embedded device style computers, application-specific integrated circuit(ASIC) based devices.

What is claimed is:
 1. A computer program product comprising: a computerreadable storage device having stored thereon: first instructionsexecutable by a device to cause the device to transmit, to a server, afirst request for a first web page; second instructions executable by adevice to cause the device to receive, from the server, the first webpage, wherein: the first web page includes at least a first set of webpage portions, and the first set of web page portions includes at leasta main content fragment; third instructions executable by a device tocause the device to receive, from the server, a first set of web pagemetadata, wherein the first set of web page metadata includes, at least:a first set of web page portion definitions corresponding to the firstset of web page portions, a first set of request dates, a first set ofexpiration dates corresponding to the first set of web page portions, afirst set of caching policies corresponding to the first set of web pageportions, a first set of related web pages, a first set of relatedadvertisements, a first site map, and a first main content fragmentcorresponding to the main content fragment; fourth instructionsexecutable by a device to cause the device to cache the first set of webpage portions based on the first set of caching policies; fifthinstructions executable by a device to cause the device to transmit, tothe server, a second request for the first web page, wherein: the secondrequest includes a second set of web page metadata, and the second setof web page metadata includes, at least: the first set of web pageportion definitions, the first set of request dates, and the first setof caching policies; sixth instructions executable by a device to causethe device to receive, from the server, a second set of web pageportions, wherein: the second set of web page portions comprises asubset of the first set of web page portions, and the second set of webpage portions comprises web page portions correlating to the subset ofthe first set of web page portions that has changed or not been cachedby the browser; seventh instructions executable by a device to cause thedevice to receive, from the server, a third set of web page metadatacorresponding to the second set of web page portions, wherein the thirdset of web page metadata includes, at least: a third set of web pageportion definitions, a third set of request dates, a third set ofexpiration dates, a third set of caching policies, a third set ofrelated web pages, a third set of related advertisements, a third sitemap, and a third main content fragment; and eighth instructionsexecutable by a device to cause the device to cache the second set ofweb page portions based on the third set of caching policies.